Mobile device connection system

ABSTRACT

A mobile device connection system may identify a mobile device of a present driver and prioritize a wireless connection between the identified mobile device and a built-in hands-free device located in a motor vehicle. In one embodiment, the mobile device connection system may include a sensor and a controller. The sensor may be configured to sense an identity of a driver when the driver is within a proximity of the motor vehicle and generate a signal based on the sensed identity. The controller may be coupled to the sensor, and it may be configured to identify the mobile device based on the signal from the sensor, search and detect the identified mobile device, and establish a wireless connection between the detected mobile device and the built-in hands-free device.

BACKGROUND

1. Field

The present invention relates generally to mobile devices, and moreparticularly to a mobile device connection system.

2. Description of the Related Art

In recent years, mobile devices, such as cellular phones, have becomemajor communication tools. However, it may be unsafe for a driver tohandle a mobile device while driving because doing so will divert thedriver's attention from the changing conditions of the road. To addressthis issue, some wireless device companies have introduced varioushands-free devices. A hands-free device may provide a communication(input-output) interface and allow a driver to use the mobile devicewithout actually holding it. Due to their convenient features, demandfor hands-free devices has been growing rapidly since theirintroduction.

To satisfy this demand, vehicle manufacturers have manufactured vehiclesthat include built-in hands-free devices or other communicationinterface devices. The built-in hands-free devices may be wirelesslyconnected to a mobile device by using a connection system. Theconnection system may detect the presence of a mobile device during aninitial pairing process. Thereafter, the connection system may connectthe paired mobile device to the hands-free device each time the pairedmobile device is detected.

Conventional connection systems may keep a pairing list, which records anumber of mobile devices that have already been paired. In the pairinglist, the mobile devices may appear in a sequence according to the orderin which they were previously paired. When there is more than one mobiledevice located in the vehicle, the mobile device that appears earlier inthe pairing list may be detected before a mobile device that appearlater in the pairing list. Once a mobile device is detected, it may beconnected to the hands-free device, whereas the not-yet-detected mobiledevices will not be connected.

Conventional connection systems lack the capability of identifying orrecognizing the identity of the present driver. As such, conventionalconnection systems suffer from several drawbacks. First, during thedetection process, conventional connection systems are unable to givepriority to the mobile device of the driver. This is especially truewhen the mobile device of the driver appears after the other mobiledevices in the pairing list. As a result, the mobile device of thedriver will not be detected until after the other mobile devices aresearched, and the connection process may be unnecessarily prolonged.

Second, conventional connection systems are unable to determine whethera mobile device belongs to a driver or a passenger. As such,conventional connection systems may detect a passenger's mobile devicebefore detecting the driver's mobile device. Instead of the driver'smobile device, conventional connection systems may connect thepassenger's mobile device to the hands-free device. As a result, thedriver may be unable to use the built-in hands-free device when othermobile devices are located in the vehicle.

Thus, there is a need to provide a mobile device connection system withimproved qualities.

SUMMARY

One or more embodiments of the present invention may provide a mobiledevice connection system. The mobile device connection system mayidentify a mobile device of a targeted person and prioritize a wirelessconnection between the identified mobile device and a communicationinterface device, such as a hands-free device.

In one embodiment, the present invention may provide a mobile deviceconnection system for wirelessly connecting a mobile device to aninput-output interface located in a motor vehicle. The mobile deviceconnection system may include a sensor configured to sense an identityof a driver when the driver is within a proximity of the motor vehicleand generate a signal based on the sensed identity, and a controllercoupled to the sensor, and configured to identify the mobile devicebased on the signal from the sensor, search and detect the identifiedmobile device, and establish a wireless connection between the detectedmobile device and the input-output interface.

In another embodiment, the present invention may provide a mobilecommunication device connection system, which may include a sensorconfigured to sense data from an identity device and generate a signalbased on the sensed data, a controller responsive to the signal, andconfigured to determine an association between the sensed data and amobile communication device, and a transceiver coupled to thecontroller, and configured to establish a wireless connection with themobile communication device based on the association between the mobilecommunication device and the sensed data.

In yet another embodiment, for example, the present invention mayinclude a method for connecting one or more mobile devices to a motorvehicle. The method may include the steps of sensing, using a sensor, anidentity of a driver, and establishing a wireless connection between oneof the mobile devices and the motor vehicle based on the sensedidentity.

BRIEF DESCRIPTION OF THE DRAWINGS

Other systems, methods, features, and advantages of the presentinvention will be or will become apparent to one with skill in the artupon examination of the following figures and detailed description. Itis intended that all such additional systems, methods, features, andadvantages be included within this description, be within the scope ofthe present invention, and be protected by the accompanying claims.Component parts shown in the drawings are not necessarily to scale, andmay be exaggerated to better illustrate the important features of thepresent invention. In the drawings, like reference numerals designatelike parts throughout the different views, wherein:

FIG. 1 is a perspective view of a vehicle having a mobile deviceconnection system according to an embodiment of the present invention;

FIG. 2 is a block diagram of a mobile device connection system accordingto an embodiment of the present invention;

FIG. 3A is a block diagram of a controller according to an embodiment ofthe present invention;

FIG. 3B is a data structure of a record according to an embodiment ofthe present invention;

FIGS. 4A-4B are perspective views of two identity devices according toan embodiment of the present invention;

FIGS. 4C-4E are various driver biometric characteristics or objectsaccording to an embodiment of the present invention;

FIG. 5 is a flowchart of a method for wirelessly connecting a mobiledevice to a motor vehicle according to an embodiment of the presentinvention; and

FIG. 6 is a flowchart of a method for associating a mobile device withan identity of a driver according to an embodiment of the presentinvention.

DETAILED DESCRIPTION

Apparatus, systems and methods that implement the embodiment of thevarious features of the present invention will now be described withreference to the drawings. The drawings and the associated descriptionsare provided to illustrate some embodiments of the present invention andnot to limit the scope of the present invention. Throughout thedrawings, reference numbers are re-used to indicate correspondencebetween reference elements. In addition, the first digit of eachreference number indicates the figure in which the element firstappears.

FIG. 1 is a perspective view of a vehicle 101 having a mobile (wireless)device connection system 100 according to an embodiment of the presentinvention. The mobile device connection system 100 may be used forwirelessly connecting a mobile device to an input-output interfacelocated in a motor vehicle, such as the vehicle 101. The vehicle 101 maybe an automobile, a car, a sport utility vehicle, a truck, or othervehicle that holds passengers.

The mobile device may be an electronic device having wireless connectioncapability. For example, the mobile device may be a cell phone, a smartphone, a personal digital assistance (PDA) device, a laptop, or anyother wireless electronic device. The wireless connection may be basedon an open wireless technology standard for exchanging data over shortdistances (using short wavelength radio transmissions) between fixed andmobile devices. For example, the wireless connection may be a Bluetoothconnection.

After being connected to the input-output interface via the wirelessconnection, the mobile device may be accessed, controlled, and/orinteracted with the input-output interface. For example, theinput-output interface may be a built-in hands-free device, throughwhich a driver may access, control, and interact with a mobile phone.

The mobile device connection system 100 may be installed in variouslocations within the vehicle 101. For example, the mobile deviceconnection system 100 may be installed adjacent to controls or a dashboard of the vehicle 101. In another example, the mobile deviceconnection system 100 may be installed underneath the driver seat of thevehicle 101. In another example, the mobile device connection system 100may be installed in the middle section of the vehicle 101.

The mobile device connection system 100 may identify the identity of adriver 140. After identifying the identity of the driver 140, the mobiledevice connection system 100 may selectively, solely and exclusivelyconnect a mobile device 142 of the identified driver 140 to theinput-output interface. During the connection process, the mobile deviceconnection system 100 may distinguish the mobile device 142 of thedriver 140 from the mobile devices 162, 172, and 182 of the passengers160, 170, and 180 respectively. As such, the mobile device connectionsystem 100 may prioritize the connection of the driver's mobile device142 over the passengers' mobile devices 162, 172, and 182.

Generally, the mobile device connection system 100 may include a sensor110 and a controller 120. The controller 120 may be coupled to thesensor 110. The driver 140 may carry an identity device 130, which maycontain identity data 132 related to the identity of the driver 140. Theidentity device 130 may be uniquely assigned to a particular driver 140,such that the sensor 110 may sense the identity of the driver 140 bysensing the identity data 132 from the identity device 130.

The identity device 130 may be an active radio frequency (RF) device ora passive RF device. If the identity device 130 is an active RF device,such as an electronic key fob, the sensor 130 may be an RF transceivercapable of receiving an RF signal from the identity device 130. If theidentity device 130 is a passive RF device, such as a stand-alone radiofrequency identification (RFID) tag, the sensor 110 may be an RFinterrogator capable of detecting and retrieving data from the RFID tag.

When the identity device 130 is within the proximity of the vehicle 101,the sensor 110 may initiate a sensing process 134. The sensing process134 may begin before the vehicle 101 is started. Depending on thedetection range of the sensor 110, the identity device 130 may be withinthe proximity of the vehicle 101 when the identity device 130 is about 1meter to about 5 meters away from the vehicle 101. As such, the sensingprocess 134 may begin as soon as the driver 140 remotely unlocks thedoor of the vehicle 101.

After the identity of the driver 140 is sensed, the sensor 110 maygenerate an identity signal 112 based on the sensed identity retrievedfrom the identity data 132. The controller 120 may receive and respondto the identity signal 112 from the sensor 110.

The controller 120 may determine the identity of the driver 140 based onthe identity signal 112. After determining the identity of the driver140, the controller 120 may determine an association between thedriver's identity and the driver's mobile device 142. The associationmay be previously recorded in the controller 120 during an initialpairing process. After identifying the driver's mobile device 142, thecontroller 120 may establish a wireless connection 144 between thedriver's mobile device 142 and the input-output interface of the vehicle101. For example, the controller 120 may establish a Bluetoothconnection between the driver's mobile device 142 and a built-inhands-free device located inside the vehicle 101.

In establishing the wireless connection 144, the controller 120 maydistinguish the driver's mobile device 142 from the passenger's mobiledevices 162, 172, and 182. The driver's mobile device 142 may receivepriority in during the search and detection process by the controller120. As such, the controller 120 may defer the searching and detectingof the passengers' mobile devices 162, 172, and 182 until the occurrenceof certain events, which may include, but is not limited to (1) thesituation where the driver's mobile device 142 has been searched but notdetected, and (2) the situation where the driver's mobile device 142 wasoffered a connection with the input-output interface, but such offer hasbeen declined or has expired.

The mobile device connection system 100 may ensure that the driver'smobile device 142 may be connected to the input-output interface once itis detected. As such, the mobile device connection system 100 may avoidthe situation in which one of the passenger's mobile devices 162, 172,and 182 may be connected to the input-output interface while thedriver's mobile device 142 remains unconnected. Additionally, the mobiledevice connection system 100 may reduce the average time spent onconnecting to the driver's mobile device 142 because less time may bespent on searching for the mobile devices that do not belong to thedriver 140. In one embodiment, for example, the mobile device connectionsystem 100 may spend no time on searching for mobile devices that do notbelong to the driver 140.

If the driver's mobile device 142 is not detected, the controller 120may then search for the passengers' mobile devices 162, 172, and 182according to a predefined sequence. Generally, the predefined sequencemay be based on the order in which the mobile devices 162, 172, and 182were initially paired with the input-output interface.

Hypothetically, the first mobile device 182 may be paired before thesecond mobile device 162, which may in turn be paired before the thirdmobile device 172. As such, the first mobile device 182 may appearbefore the second mobile device 162 in the predefined sequence.Similarly, the second mobile device 162 may appear before the thirdmobile device 172 in the predefined sequence.

According to the predefined sequence, the controller 120 may firstsearch for the first mobile device 182. If the first mobile device 182is detected, the controller 120 may establish a first wirelessconnection 184 between the first mobile device 182 and the input-output(I/O) interface.

If the first mobile device 182 is not detected, the controller 120 mayfollow the predefined sequence and continue to search for the secondmobile device 162. If the second mobile device 162 is detected, thecontroller 120 may establish a second wireless connection 164 betweenthe second mobile device 162 and the I/O interface.

Otherwise, the controller 120 may continue to search for the thirdmobile device 172 and attempt to establish a third wireless connection174 between the third mobile device 172 and the I/O interface. Thisprocess may continue to additional mobile devices.

Although FIG. 1 shows that only the driver 140 carries the identitydevice 130, the passengers 160, 180, and 170 may each carry a differentidentity device, which may contain identity data related to the identityof each passenger 160, 170, or 180. Assigning each passenger with adifferent identity device may be beneficial because each passenger maytake turns driving the vehicle 101. For example, when the firstpassenger 180 becomes the driver, the mobile device connection system100 may grant priority to the first mobile device 182 for establishingthe first wireless connection 184 with the I/O interface.

According to an embodiment of the present invention, the mobile deviceconnection system 100 may be used in conjunction with multiple identitydevices. As shown in FIG. 2, a motor vehicle may contain a firstpassenger 210 carrying a first identity device 212 and a first mobiledevice 220, a second passenger 230 carrying a second identity device 232and a second mobile device 240, and a third passenger 250 carrying athird identity device 252 and a third mobile device 260. The firstidentity device 212 may store first identity data 214, which may berelated to the identity of the first passenger 210. The second identitydevice 232 may store second identity data 234, which may be related tothe identity of the second passenger 230. The third identity device 252may store third identity data 254, which may be related to the identityof the third passenger 250.

Each of the first 210, second 230, and third 250 passengers maypotentially become the driver. For example, the first passenger 210 mayoccupy the driver seat, while the second passenger 230 may occupy apassenger seat located next to the driver seat and the third passenger250 may occupy another passenger seat located behind the driver seat. Inone situation, the person who occupies the driver seat may be presumedto be the driver. Because each identity device 220, 240, or 260 ispositioned close to the passenger with which it is purported toidentify, the identity device may be used for indicating the position ofthe passenger. Hence, a distance measured between the identity deviceand the driver seat may be used for determining who the driver is. Morespecifically, the driver may be a passenger having the identity devicethat maintains the shortest distance from the driver seat.

The sensor 110 may be placed at a reference position 207, which may bean area close to the driver seat. In one embodiment, for example, thereference position 207 may be located adjacent to the steering wheel. Inanother embodiment, for example, the reference position 207 may belocated above the driver's seat. In yet another embodiment, for example,the reference position 207 may be located under the driver's seat.

The first identity device 212 may maintain a first distance 201 from thereference position 207. The second identity device 232 may maintain asecond distance 203 from the reference position 207. The third identitydevice 252 may maintain a third distance 205 from the reference position207. The sensor 110, being placed at the reference position 207, maysense and determine each of the first 201, second 203, and third 205distances.

In one embodiment, the sensor 110 may estimate the first 201, second203, and third 205 distances by detecting the signal strength of thedata signals received from the first 212, the second 232, and the third252 identity devices. Typically, strong signal strength may indicate ashort distance whereas weak signal strength may indicate a longdistance. For the example presented in FIG. 2, the signal strength ofthe first identity device 212 at the reference position 207 may bestronger than those of the second 232 and third 252 identity devices.The sensor 110 may rank the signal strengths of the first 212, second232, and third 252 identity devices. Accordingly, the sensor 110 mayestimate that the first distance 201 may be shorter than the second 203and third 205 distances. Accordingly, the sensor 110 may determine thatthe first identity device 212 belongs to the present driver, and it maybe ready to sense the identity of the driver.

After determining that the first identity device 212 belongs to thepresent driver, the sensor 110 may selectively sense the first identitydata 214 from the first identity device 212 while ignoring the second234 and third 254 identity data from the respective second 232 and third252 identity devices. The sensor 110 may generate the identity signal112 based on the sensed identity data. The controller 120 may receivethe identity signal 112 via a hard wired or wireless connection. Thecontroller 120 may process the information embedded in the identitysignal 112 and thereby associating the driver's mobile device with thesensed identity data. For example, the controller 120 may associate thefirst mobile device 220 with the first identity data 214.

Next, the controller 120 may search for the associated mobile device bysending and receiving an antenna signal 277 via an antenna 278. Theantenna 278 may broadcast a wireless detecting signal 290 for detectingthe associated mobile device, which may be the first mobile device 220in this example. If the associated mobile device is detected, thecontroller 120 may establish a wireless connection between the detectedmobile device and the input-output (I/O) interface 270 (a.k.a.communication interface). If the associated mobile device is notdetected, the controller 120 may begin searching and detecting othermobile devices according to a predefined sequence.

For example, the controller 120 may first search for the first mobiledevice 220 because the first mobile device 220 is associated with thefirst identity data 214. If the first mobile device 220 is detected, thecontroller 120 may establish a first wireless connection 280 between thefirst mobile device 220 and the I/O interface 270. Otherwise, thecontroller 120 may establish a second wireless connection 282 betweenthe second mobile device 240 and the I/O interface 270, oralternatively, the controller 120 may establish a third wirelessconnection 284 between the third mobile device 260 and the I/O interface270.

After the wireless connection is established between the detected mobiledevice and the I/O interface 270, the driver may access, control, andinteract with the connected mobile device via the I/O interface 270. TheI/O interface 270 may include one or more input devices and/or outputdevices. In one embodiment, for example, the I/O interface 270 mayinclude a microphone 274, a touch screen 276, and/or a key pad (notshown). As such, the I/O device 270 may receive audio and data inputsfor the connected mobile device. In another embodiment, for example, theI/O interface 270 may include a speaker 272 and/or a display screen (notshown). As such, the I/O interface 270 may deliver audio and videooutputs for the connected mobile device.

The wireless connection between the connected mobile device and the I/Ointerface 270 may be direct or indirect. If the wireless connection isdirect, the connected mobile device may communicate with the I/Ointerface 270 without the help of the controller 120. In the directconnection mode, the I/O interface 270 may include a transceiver (notshown) for sending and receiving wireless signals.

If the wireless connection is indirect, the connected mobile device maycommunicate with the I/O interface 270 via the controller 120. That is,a wireless connection may be established between the connected mobiledevice and a transceiver that controls the antenna 278. For example, thecontroller 120 may transmit an audio output signal 271 from theconnected mobile device to the speaker 272. In another example, thecontroller 120 may transmit an audio input signal 273 from themicrophone 274 to the connected mobile device. In another example, thecontroller 120 may transmit a visual output signal 275 from theconnected mobile device to the touch screen 276.

FIG. 3A shows a block diagram of a controller 120 according to anembodiment of the present invention. Generally, the controller 120 mayinclude a processor 310 and a memory 320. The processor 310 may becoupled to the memory 320. The processor 310 can be any computing devicecapable of receiving data, processing the received data, and outputtingthe processed data. The processor 310 may be implemented using hardware,software, firmware, middleware, microcode, or any combination thereof.The processor 310 may be an Advanced RISC Machine (ARM), a computer, adigital signal processor (DSP), a microprocessor, a processor chip,and/or any other device capable of processing data. The memory 320 mayinclude and/or store various routines and/or data. The term “memory”includes, but is not limited to, random access memory (RAM), flashmemory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk,removable disk, CD-ROM, DVD, Blu-ray disk, wireless channels, and/orvarious other media capable of storing, containing or carryinginstruction(s) and/or data.

The memory 320 may store one or more records. For example, FIG. 3B showsa data structure of a record 322 according to an embodiment of thepresent invention. The record 322 may include an identity field 324 andat least a first mobile device field 325. During an initial pairingprocess, the processor 310 may write the identity data of a driver intothe identity field 324 of the record 322. For example, the processor 310may write the identity data “1234” into the identity field 324 of thenew record 322.

The identity data “1234” may be sensed from an identity device asdiscussed in FIGS. 1 and 2. Alternatively, the identity data “1234” maybe generated by the processor 310, and it may be used for representingone or more sensed biometric characteristics of a driver.

The processor 310 may detect a first mobile device of the driver, and itmay write a first mobile device code into the first mobile device field325 of the record 322. For example, the processor 310 may write thefirst mobile device code “DROID_(—)8864” into the first mobile devicefield 325 to record that the driver's first mobile device is an Androidsmart phone.

Optionally, if the driver has a second mobile device, the processor 310may write a second mobile device code into the second mobile devicefield 326. For example, the processor 310 may write a second mobiledevice code “BLACKBERRY_(—)7575” into the second mobile device field 326to record that the driver's second mobile device is a Blackberry PDAdevice. Similarly, if the driver has a third mobile device, theprocessor 310 may write a third mobile device code into the third mobiledevice field 327. For example, the processor 310 may write a thirdmobile device code “STORM” into the third mobile device field 327 torecord that the driver's third mobile device is a Storm smart phone.Each of the first, second, and third mobile device codes may be used foridentifying the first, second, and third mobile devices respectively.Each record 322 may have as many mobile device fields as the size of thememory 320 may allow.

After being created, updated, and stored, the record 322 may be usedlater for associating a sensed identity of a driver to a particularmobile device. Referring again to FIG. 3A, the processor 310 may receivethe identity signal 112 from the sensor 110. The processor 310 mayextract the sensed identity data from the received identity signal 112.The process 310 may then access the memory 320 and match the sensedidentity data against the identity field 320 of the records 322. When amatch is found, the processor 310 may decode the first mobile devicecode, which may be stored in the first mobile device field 325 of thematched record 322. The processor 310 may use the decoded information toidentify the first mobile device, and thereby establishing anassociation between the sensed identity data and the identified firstmobile device.

The processor 310 may search and detect the first mobile device based onthe established association. A transceiver 330 may be coupled to theprocessor 310, and it may be used for generating and receiving theantenna signal 277 during the search and detect process. In oneembodiment, for example, the transceiver 330 may be a Bluetoothtransceiver. If the first mobile device is detected, the processor 310may establish a wireless connection between the detected first mobiledevice and the I/O interface 270 as shown in FIG. 2. In one embodiment,for example, the wireless connection may include a Bluetooth connection.

If the first mobile device is not detected, the processor 310 may decodethe second mobile device code, which may be stored in the second mobiledevice field 326 of the matched record 322. After decoding the secondmobile device code, the processor 310 may identify the second mobiledevice, and thereby establishing an association between the sensedidentity data and the identified second mobile device. The processor 310may search and detect the second mobile device based on the establishedassociation. If the second mobile device is detected, the processor 310may establish a wireless connection between the detected second mobiledevice and the I/O interface 270 as shown in FIG. 2.

If the second mobile device is not detected, the processor 310 mayrepeat the above process until an associated mobile device is detected,or alternatively, until the matched record 322 indicates that the driverhas no more mobile device. In the event that the processor 310 does notdetect any associated mobile device for a particular driver, theprocessor 310 may begin detecting other mobile devices. The processor310 may wirelessly connect the detected mobile device to the I/Ointerface 270.

In order to access, control, and interact with the I/O interface 270,the processor 310 may be coupled to an input-output (I/O) driver block340, which may include one or more input or output drivers. In oneembodiment, for example, the I/O driver block 340 may include an audiooutput driver 342 for generating the audio output signal 271. In anotherembodiment, for example, the I/O driver block 340 may include an audioinput driver 344 for receiving the audio input signal 272. In yetanother embodiment, for example, the I/O driver block 340 may include avideo output driver 346 for generating the video output signal 273.

Although FIG. 3A shows that the processor 310 and the memory 320 areimplemented separately, the processor 310 and the memory 320 may beimplemented by a single integrated circuit according to an alternativeembodiment of the present invention. Moreover, the transceiver 330 andthe I/O driver block 340 may be combined to form a single device, whichmay be coupled to the single integrated circuit comprising the processor310 and the memory 320.

As discuss previously in FIG. 1, the sensor 110 may be used for sensingthe identity of the driver, and it may generate an identity signal 112based on the sensed identity. The identity of the driver may be storedor preprogrammed into an identity device. The identity device may be anactive radio frequency (RF) device or a passive radio frequency (RF)device.

The active RF device may actively transmit the identity data to thesensor 110 without the initiation of the sensor 110. For example, asshown in FIG. 4A, the active RF device may be an electronic key fob 410,which may include an unlock button 412 and a lock button 414. Theelectronic key fob 410 may include a memory device for storing theidentity data. When the unlock button 412 is depressed, the electronickey fob 410 may send an unlocking signal to the motor vehicle forunlocking one or more doors thereof. The unlocking signal may beembedded with the identity data, which may be received and sensed by thesensor 110.

The active RF device may allow the sensor 110 to sense the identity ofthe driver even when the driver is outside the motor vehicle. Hence, thecontroller 120 may begin searching and detecting the driver's mobiledevice before the driver opens or starts the motor vehicle.Advantageously, using the active RF device as an identity device mayallow the driver's mobile device to be wireless connected to the I/Ointerface 270 before the driver enters the motor vehicle.

The active RF device may be any device capable of storing the identitydata and transmitting the identity data. As such, the active RF devicemay be integrated with a mobile device capable of transmitting shortrange RF signals. Alternatively, the active RF device may be an activeradio frequency identification (RFID) tag, which may periodically,repeatedly, or continuously broadcast a short range RF signal thatcarries the identity data.

The passive RF device may passively transmit the identity data to thesensor 110 upon receiving a request from the sensor 110. For example, asshown in FIG. 4B, the passive RF device may be a passive radio frequencyidentification (RFID) tag 420. The passive RFID tag 420 may receive aninterrogation signal from the sensor 110, and it may reflect theinterrogation signal back to the sensor 110 when the interrogationsignal is in resonance with the passive RFID tag 420. As such, thesensor 110 may sense the identity data from the passive RFID tag 420 ifthe interrogation signal is at a frequency that resonates with that ofthe passive RFID tag 420.

The passive RF device, such as the passive RFID tag 420, may beconvenient to carry because of its light weight and small size.Accordingly, the driver may carry the passive RFID tag 420 with a keychain or in a wallet. Moreover, the passive RFID tag 420 may be embeddedin a flash memory card, such as a micro SD card, which is commonly usedas a storage means for mobile device. Advantageously, using the passiveRF device as an identity device may allow the driver's mobile device tobe wireless connected to the I/O interface 270 before the driver entersthe motor vehicle.

Besides sensing the identity data from the identity device, the sensor110 may include a biometric sensor, which may sense the identity of thedriver by sensing one or more biometric characteristics of the driver.As shown in FIG. 4C, for example, a vocal feature 430 may be a biometriccharacteristic of a driver. The sensor 110 may be a voice sensor, whichmay sense the identity of the driver by recognizing the vocal feature430 of the driver. In one embodiment, the voice sensor may be astand-alone device. In another embodiment, the voice sensor may beintegrated with the microphone 274 as shown in FIG. 2.

As shown in FIG. 4D, for example, a fingerprint pattern 440 may be abiometric characteristic of a driver. The sensor 110 may be afingerprint sensor, which may sense the identity of the driver byrecognizing the fingerprint pattern 440 of the driver. In oneembodiment, the fingerprint sensor may be a stand-alone device. Inanother embodiment, the fingerprint sensor may be integrated with apower on (ignition) button (not shown) of the motor vehicle.

As shown in FIG. 4E, for example, a retina pattern 440 may be abiometric characteristic of a driver. The sensor 110 may be a retinasensor, which may sense the identity of the driver by recognizing theretina pattern 440 of the driver. In one embodiment, the retina sensormay be a stand-alone device. In another embodiment, the retina sensormay be integrated with a camera (not shown) installed inside the motorvehicle.

FIG. 5 shows a flowchart of a method 500 for wirelessly connecting adriver's mobile device to a motor vehicle according to an embodiment ofthe present invention. In step 502, an identity of a driver may besensed by using a sensor. Depending on the sensing scheme, the identityof the driver may be sensed by receiving identity data from an identitydevice or by collecting one or more biometric characteristics from thedriver. For example, the identity of the driver may be sensed by sensingidentity data from a passive radio frequency device or from an activeradio frequency device. In another example, the identity of the drivermay be sensed by using a biometric sensor to sense the biometriccharacteristic of the driver. The biometric characteristic of the drivermay include the driver's vocal features, fingerprint pattern, and/orretina pattern.

In step 504, a determination may be made regarding whether the identityof the driver is sensed. If the identity of the driver is sensed, themethod 500 may proceed to step 506. Otherwise, the method 500 may returnto step 502.

In step 506, a mobile device may be associated with the sensed identity.Typically, a controller may be connected to the sensor, and it mayreceive the sensed identity from the sensor. The controller may have apredefined list of mobile devices, each of which may be assigned to aparticular driver. The controller may use the predefined list, as wellas the sensed identity of the present driver, to identify the presentdriver's mobile device.

Next, in step 508, the associated mobile device may be searched by thecontroller. For example, detection signals may be transmitted fordetecting the presence of the associated mobile device. During thesearching and detecting process, any other devices that are notassociated to the sensed identity of the present driver may be ignored.As such, the associated mobile device may receive priority in beingsearched and detected.

In step 510, a determination may be made regarding whether theassociated mobile device is detected. If the associated mobile device isdetected, the method 500 may proceed to step 518. Otherwise, the method500 may proceed to step 512.

In step 518, the detected mobile device may be wirelessly connected toan input-output interface located in the motor vehicle. The detectedmobile device may be wirelessly connected to the input-output interfaceby using the controller. In one embodiment, for example, the controllermay establish a short range radio frequency connection, such as aBluetooth connection. The input-output interface may be a communicationinterface, such as a hands-free device and/or a touch screen. Theinput-output interface may transmit inputs entered by the driver to theconnected mobile device, and it may deliver outputs from the connectedmobile device to the driver.

If the associated mobile device is not detected, the method 500 mayproceed to step 512, in which a determination may be made regardingwhether there is any more mobile device to be associated to the sensedidentity of the present driver. If there is another mobile device to beassociated to the sensed identity of the present driver, the method 500may return to step 506. Otherwise, the method 500 may proceed to step514.

In step 514, the other mobile devices may be searched and detected in apredefined sequence. For example, the predefined sequence may beaccording to the order in which the other mobile devices are previouslydiscovered and paired. The other mobile devices may belong to one ormore passengers, or they may be the unpaired mobile devices of thepresent driver.

In step 516, a determination may be made regarding whether one of theother mobile devices is detected. If one of the other mobile devices isdetected, the method 500 may proceed to step 518, in which the detectedmobile device may be wirelessly connected to the input-output interface.Otherwise, the method 500 may return to step 514, in which the othermobile devices may be searched and detected.

FIG. 6 shows a flowchart of a method 600 for associating a mobile devicewith the identity of a driver according to an embodiment of the presentinvention. Particularly, the method 600 may exemplify and elaborate theimplementation of step 506 of the method 500 as discussed in FIG. 5. Instep 602, the sensed identity may be matched against an identity fieldof a record. The record may be previously created and stored in thecontroller during an initial pairing process, during which informationrelated to a particular driver's identity, as well as the driver'smobile device, may be recorded.

In step 604, a determination may be made regarding whether a matchedrecord is found. If a matched record is found, the method 600 mayproceed to step 606. Otherwise, the method 600 may proceed to step 608.

In step 606, a mobile device may be identified based on a mobile devicefield of the matched record. Accordingly, the identified mobile devicemay be associated with the identity of the present driver.

If a matched record is not found in step 604, the method 600 may proceedto step 608, in which a determination may be made regarding whether allthe records are searched. If there is no more record to be searched, themethod 600 may proceed to step 612. Otherwise, the method 600 mayproceed to step 610, in which a next record may be searched. Aftersearching the next record, the method 600 may return to step 604, inwhich a determination may be made regarding whether the searchedrecord's identity field matches the sensed identity of the presentdriver.

In step 612, a new record for the sensed identity may be created. Instep 614, information related to a new mobile device may be entered in amobile device field of the new record. If the driver does not have a newmobile device to be added to the new record, the method 600 may beterminated without associating any mobile device with the sensedidentity. Otherwise, the method 600 may proceed to step 606, in whichthe new mobile device may be identified as the present driver's mobiledevice.

Although the embodiments discussed in FIGS. 1-6 show that the mobiledevice connection system 100, and the method 500, can be applied to amotor vehicle, such as a car, the mobile device connection system 100,and the method 500, may be applied to other settings as well. Generally,the mobile device connection system 100, and the method 500, may beapplied to home, office, and other facilities at which an input-outputinterface 270 may be installed.

For example, the mobile device connection system 100, and the method500, may be used for sensing an identity of a selected home member andthen wirelessly connecting a laptop computer of the selected home memberto a television display screen and/or a home entertainment system. Inanother example, the mobile device connection system 100, and the method500, may be used for sensing an identity of a selected office staffmember and then wirelessly connecting a laptop computer of the selectedoffice staff member to a projector. In another example, the mobiledevice connection system 100, and the method 500, may be used forsensing an identity of a selected user and then wirelessly connecting acell phone of the selected person to a portable global positioningsystem (GPS).

Moreover, the mobile device connection system 100, and the method 500,may be adjustable in granting priority to the mobile devices of variouspeople. For example, the mobile device connection system 100, and themethod 500, may grant priority to the mobile device of a particularhouse member. In another example, the mobile device connection system100, and the method 500, may grant priority to the mobile device of aparticular staff member of an office. In another example, the mobiledevice connection system 100, and the method 500, may grant priority tothe mobile device of a selected user.

Exemplary embodiments of the invention have been disclosed in anillustrative style. Accordingly, the terminology employed throughoutshould be read in a non-limiting manner. Although minor modifications tothe teachings herein will occur to those well versed in the art, itshall be understood that what is intended to be circumscribed within thescope of the patent warranted hereon are all such embodiments thatreasonably fall within the scope of the advancement to the art herebycontributed, and that that scope shall not be restricted, except inlight of the appended claims and their equivalents.

What is claimed is:
 1. A mobile device connection system for wirelesslyconnecting a mobile device to a transceiver located in a motor vehiclehaving a driver area including a driver seat and a steering wheel, and apassenger area including a passenger seat, comprising: a memory forstoring an association or a pairing between a key fob of a user of themotor vehicle and a mobile device; a sensor positioned in the driverarea and configured to: sense a first key fob and a first identity dataof a first user during a first pairing process, and sense a second keyfob and a second identity data of a second user during a second pairingprocess; a controller coupled to the sensor and the memory, andconfigured to: store a first association or pairing between the firstidentity data and a first mobile device of the first user that isseparate from the first key fob, store a second association or pairingbetween the second identity data and a second mobile device of thesecond user that is separate from the second key fob, designate thefirst user as a driver of the motor vehicle when or after a senseddistance of the first key fob is less than a sensed distance of thesecond key fob, designate the second user as the driver when or after asensed distance of the second key fob is less than a sensed distance ofthe first key fob, establish a first wireless connection between amobile device of the driver and the transceiver and ignore establishinga second wireless connection between a previously paired mobile deviceof a passenger of the motor vehicle and the transceiver for expeditingor enhancing the establishment of the first wireless connection, andestablish the second wireless connection when or after the firstwireless connection cannot be established and ignore establishing athird wireless connection between a previously unpaired mobile deviceand the transceiver; and an input-output interface coupled to thecontroller, and configured to receive input from and generate output forthe mobile device of the driver via the first wireless connection whenor after the first user or the second user is designated as the driverand the first wireless connection can be established.
 2. The system ofclaim 1, wherein: before the driver enters the motor vehicle or beforethe motor vehicle is started, the sensor is configured to sense thefirst identity data or the second identity data, and the controller isconfigured to detect the first mobile device of the first user when orafter the sensed distance of the first key fob indicates that the firstuser is the driver but before the driver enters the motor vehicle orbefore the motor vehicle is started.
 3. The system of claim 1, wherein:the memory is configured to store one or more records, each recordhaving an identifier field and a mobile device field, and the controlleris configured to: match the sensed first identity data against theidentifier field of the one or more records, and detect the first mobiledevice based on the mobile device field of the matched record.
 4. Thesystem of claim 1 wherein the first key fob is an electronic keyconfigured to transmit a wireless signal to the motor vehicle, thewireless signal detectable by the sensor, and the wireless signalembedding the first identity data.
 5. The system of claim 1, wherein thesensor is configured to sense the first identity data of the driver bysensing a biometric characteristic of the first user.
 6. The system ofclaim 5, wherein the biometric characteristic is selected from a groupconsisting of a fingerprint, a voice pattern, a retina pattern, andcombinations thereof.
 7. A mobile communication device connection systemof a motor vehicle having a driver area including a driver seat and asteering wheel, and a passenger area including a passenger seat,comprising: a memory for storing an association or a pairing between akey fob of a user of the motor vehicle and a mobile communicationdevice; a sensor positioned in the driver area and configured to: sensea first identity data of a first user from a first key fob within adetection range of the sensor and a second identity data of a seconduser from a second key fob within the detection range of the sensor,sense a first distance between a distance reference in the driver areaand the first key fob and a second distance between the distancereference and the second key fob, and generate a signal based on thesensed first and second identity data and the sensed first and seconddistances; a controller positioned within the motor vehicle andresponsive to the signal, and configured to: store a first associationor pairing between the first identity data and a first mobilecommunication device of the first user that is separate from the firstkey fob, store a second association or pairing between the secondidentity data and a second mobile communication device of the seconduser that is separate from the second key fob, designate the first useras a driver of the motor vehicle when or after the sensed first distanceis less than the sensed second distance, and designate the second useras the driver when or after the sensed second distance is less than thesensed first distance; and a transceiver positioned within the motorvehicle and coupled to the controller, and configured to: establish afirst wireless connection with the first mobile communication device,ignore establishing a second wireless connection between a previouslypaired mobile communication device of a passenger of the motor vehicleand the transceiver for expediting or enhancing the establishment of thefirst wireless connection, and establish the second wireless connectionwhen or after the first wireless connection cannot be established andignore establishing a third wireless connection between a previouslyunpaired mobile communication device and the transceiver; and acommunication interface coupled to the controller, and configured toreceive input from and generate output for the first mobilecommunication device via the first wireless connection when or after thefirst user is designated as the driver and the first wireless connectioncan be established.
 8. The system of claim 7, wherein: the memory isconfigured to store one or more records, each record having anidentifier field and a mobile communication device field, and thecontroller is further configured to: receive the signal from the sensor,extract the sensed first identity data of the first key fob from thesignal when or after the sensed first distance is less than the sensedsecond distance, match the sensed first identity data against theidentifier field of one of the records, and associate the sensed firstidentity data with the first mobile communication device based on themobile communication device field of the matched record.
 9. The systemof claim 8, wherein the first key fob is configured to transmit awireless signal to the motor vehicle, the wireless signal detectable bythe sensor, and the wireless signal embedding the first identity data.10. The system of claim 7, wherein the first key fob is one of an activeradio frequency device and a passive radio frequency device.
 11. Thesystem of claim 7, wherein the first wireless connection is a blue-toothconnection.
 12. A method for connecting one or more mobile devices to amotor vehicle having a driver area, including a driver seat and asteering wheel, and a passenger area including a passenger seat,comprising: sensing, using a sensor positioned in the driver area, afirst key fob and a first identity data of a first user during a firstpairing process and a second key fob and a second identity data of asecond user during a second pairing process; storing, in a memory, afirst association or pairing between the first identity data and a firstmobile device of the first user and a second association or pairingbetween the second identity data and a second mobile device of thesecond user; generating, using the first key fob, a first signal havinga first signal wave characteristic and embedding the first identitydata; generating, using the second key fob, a second signal having asecond signal wave characteristic and embedding the second identitydata; sensing, using the sensor, the first identity data and the firstsignal wave characteristic when the first key fob is within a proximityof the motor vehicle; sensing, using the sensor, the second identitydata and the second signal wave characteristic when the second key fobis within the proximity of the motor vehicle; determining, using acontroller positioned within the motor vehicle and coupled to thesensor, a first distance between a distance reference in the driver areaand the first key fob based on the sensed first signal wavecharacteristic, and determining, using the controller, a second distancebetween the distance reference and the second key fob based on thesensed second signal wave characteristic; designating, using thecontroller, the first key fob as a key fob of a driver when thedetermined first distance is less than the determined second distanceand designating, using the controller, the second key fob as the key fobof the driver when the determined second distance is less than thedetermined first distance; searching for, using the controller,establishing a first wireless connection between a mobile deviceassociated with the sensed identity data of the designated key fob ofthe driver and the transceiver; and searching for, using the controller,establishing a second wireless connection between a previously pairedmobile device and the transceiver when the first wireless connectioncannot be established and ignoring a third wireless connection betweenan unpaired paired mobile device and the transceiver.
 13. The method ofclaim 12, wherein establishing the first wireless connection includes:detecting the mobile device associated with the sensed identity data ofthe designated key fob of the driver, and wirelessly connecting thedetected mobile device to the transceiver.
 14. The method of claim 13,wherein detecting the mobile device associated with the sensed identitydata of the designated key fob of the driver includes: matching thesensed identity data of the designated key fob of the driver against oneor more records, and identifying the mobile device associated with thesensed identity data of the designated key fob of the driver based onthe matched record.
 15. The method of claim 13, wherein detecting themobile device associated with the sensed identity data of the designatedkey fob of the driver includes ignoring the rest of the one or moremobile devices.
 16. The method of claim 12, wherein each of the firstand the second key fobs is one of a passive radio frequency device andan active radio frequency device when the each of the first and thesecond key fobs is within about 1 m to about 5 m of the motor vehicle.17. The method of claim 12, wherein, sensing the first signal wavecharacteristic includes sensing a first signal strength or amplitude ofthe first signal, and sensing the second signal wave characteristicincludes sensing a second signal strength or amplitude of the secondsignal, and determining the first distance is based on the sensed firstsignal strength or amplitude and determining the second distance isbased on the sensed second signal strength or amplitude, such that thefirst distance is determined to be less than the second distance whenthe sensed first signal strength or amplitude is greater than the sensedsecond signal strength or amplitude, and the second distance isdetermined to be less than the first distance when the sensed secondsignal strength or amplitude is greater than the sensed first signalstrength or amplitude.
 18. The system of claim 1 wherein the sensor isfurther configured to sense a third key fob and a third identity data ofa third user during a third pairing process, and the controller isconfigured to: store a third association or pairing between the thirdidentity data and a third mobile device of the third user, assign ahigher priority to the second association or pairing over the thirdassociation or pairing when the second pairing process is performedbefore the third pairing process, and assign a higher priority to thethird association or pairing over the second association or pairing whenthe third pairing process is performed before the second pairingprocess, establish a wireless connection between the second mobiledevice and the transceiver when the first wireless connection cannot beestablished and the second association or pairing has the higherpriority over the third association or pairing, and establish a wirelessconnection between the third mobile device and the transceiver when thefirst wireless connection cannot be established and the thirdassociation or pairing has the higher priority over the secondassociation or pairing.
 19. The system of claim 1 wherein: the sensor isconfigured to sense the distance of the first key fob or the first useras the first key fob approaches the motor vehicle and is within apredetermined distance of the motor vehicle, and the controller isconfigured to designate the first user as the driver when the senseddistance of the first key fob indicates that the first user is thedriver, before the first user is in the motor vehicle in order toexpedite or enhance the establishment of the first wireless connection.20. The system of claim 1 wherein: the sensor is further configured tosense a third key fob and a third identity data of a third user during athird pairing process, and the controller is configured to: store athird association or pairing between the third identity data and a thirdmobile device of the third user, receive a user-defined priority for thesecond association or pairing or for the third association or pairing,and when the first wireless connection cannot be established, establisha wireless connection between the transceiver and one of the secondmobile device and the third mobile device based on the user-definedpriority.
 21. The method of claim 12 further comprising: establishing awireless connection between the transceiver and an unpaired mobiledevice without any associated identity data stored in the memory whenwireless connections with mobile devices of users having associated orpaired identity data stored in the memory cannot be established.